Systems and methods for in-application and in-browser purchases

ABSTRACT

A system may identify a purchase transaction request from a merchant application and generate an in-app payment cryptogram for the purchase transaction request based on a limited use payment credential (LUPC). The in-app payment cryptogram may be provided to the merchant application. The merchant application may transmit the in-app payment cryptogram to a merchant computing device. A request may be received from a payment network to update the LUPC. A security library may be executed to determine that the client device is secure. The execution of the security library may generate a device attestation response, and the device attestation response is transmitted to the payment network. An updated LUPC may be received from the payment network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to,co-pending U.S. Patent Non-provisional Application entitled “SYSTEMS ANDMETHODS FOR IN-APPLICATION PURCHASES,” filed on Nov. 9, 2015 andassigned application Ser. No. 14/936,294, which claims priority to U.S.Provisional Application entitled “SYSTEMS AND METHODS FOR IN-APPLICATIONPURCHASES,” filed on Jun. 26, 2015 and assigned application No.62/185,427, in which are incorporated by reference as if set forthherein in their entireties.

FIELD

The present disclosure relates to systems and methods for conductingin-application and in-browser purchases from user devices.

BACKGROUND

Modern consumers often shop online with increasing regularity. In fact,e-commerce comprises a significant portion of total sales for manymerchants. The increase in e-commerce transactions may be attributablein part to convenience and the ease of completing transactions. However,as consumers become accustomed to the ease of online transacting,inconveniences or inefficiencies may frustrate consumers into abandoningpurchases that they would otherwise complete. For example, a consumermay become frustrated when their purchase account card is out of reachor the page resets causing personal information already entered to belost. Such seemingly small hurdles to completing the transaction mayscuttle the purchase.

The availability of digital wallet applications increases as more usersacquire digital devices. Digital wallets may streamline the paymentprotocol in some instances and avoid some of the potential pitfalls oftraditional web transactions. However, stored transaction accountinformation makes digital wallets and user devices prime targets fortheft and fraud. Thus, the use of a digital wallet for in-applicationand/or in-browser purchases may present increased security risks.

SUMMARY

A system, method, and computer readable medium (collectively, the“system”) is disclosed for in-application purchases executed from abrowser or merchant application. The system may be configured to performoperations and/or steps comprising receiving a transaction request froma user device, and requesting an in-app cryptogram from a networksoftware development kit (SDK) on the user device. The in-app cryptogrammay include an unpredictable number, an application transaction counter(ATC), and a card verification result (CVR), and the ATC may beextracted from a limited use payment credential (LUPC). The system maytransmit a token, a token expiry, and a token data block for anassessment by a payment network, with the token data block including thetoken, the token expiry, the ATC, and/or the in-app cryptogram. Thesystem may further receive a request from the payment network to updatethe LUPC on the user device, and attest that the user device is securein response to the request from the payment network to refresh the LUPCon the user device.

In various embodiments, the assessment by the payment network mayinclude comparing a payment cryptogram to the in-app cryptogram with thepayment cryptogram being calculated by the payment network. The paymentnetwork may approve a transaction in response to the payment cryptogrammatching the in-app cryptogram. The system may be configured to performfurther operations including generating a payment payload including thetoken, the token expiry, the ATC, and the in-app cryptogram; encryptingthe payment payload using a merchant key; and transmitting, by thewallet provider, the payment payload to a merchant associated with themerchant key. The system may also compute at least one of a signature ora message authentication code on the payment payload using a walletprovider key. A refreshed LUPC may be received from the payment networkin response to the attesting the user device is secure. The system mayalso receive a rejection in response to the attesting the user device issecure, and retry to refresh the LUPC in response to the receiving therejection. The forgoing features and elements may be combined in variouscombinations without exclusivity, unless expressly indicated hereinotherwise. These features and elements as well as the operation of thedisclosed embodiments will become more apparent in light of thefollowing description and accompanying drawings.

BRIEF DESCRIPTION

The subject matter of the present disclosure is particularly pointed outand distinctly claimed in the concluding portion of the specification. Amore complete understanding of the present disclosure, however, may beobtained by referring to the detailed description and claims whenconsidered in connection with the drawing figures, wherein like numeralsdenote like elements.

FIG. 1 illustrates an exemplary system for carrying out in-applicationtransactions, in accordance with various embodiments;

FIG. 2 illustrates exemplary software and hardware components incommunication for carrying out in-application transactions, inaccordance with various embodiments;

FIG. 3 illustrates a process for initiating an in-applicationtransaction, in accordance with various embodiments;

FIG. 4 illustrates a process for completing an in-applicationtransaction, in accordance with various embodiments;

FIG. 5 illustrates exemplary software and hardware components incommunication for carrying out in-application transactions, inaccordance with various embodiments; and

FIG. 6A-6B illustrates a process for completing in-application and/orin-browser transactions using limited use purchase credentials, inaccordance with various embodiments.

DETAILED DESCRIPTION

The detailed description of various embodiments herein makes referenceto the accompanying drawings and pictures, which show variousembodiments by way of illustration. While these various embodiments aredescribed in sufficient detail to enable those skilled in the art topractice the disclosure, it should be understood that other embodimentsmay be realized and that logical and mechanical changes may be madewithout departing from the spirit and scope of the disclosure. Thus, thedetailed description herein is presented for purposes of illustrationonly and not of limitation. For example, the steps recited in any of themethod or process descriptions may be executed in any order and are notlimited to the order presented. Moreover, any of the functions or stepsmay be outsourced to or performed by one or more third parties.Furthermore, any reference to singular includes plural embodiments, andany reference to more than one component may include a singularembodiment.

As used herein, a “digital wallet” includes software and/or anelectronic device that facilitates individual e-commerce and m-commercetransactions. The digital wallet may operate by aggregating thetransaction account holder's payment and billing information and servingas the merchant of record, and/or passing through the transactionaccount holder's payment and billing information to the end merchant.Examples of digital wallets currently available include Apple Pay®,Passbook®, and Google Wallet™.

The present disclosure provides a system, method, and computer programproduct for conducting online transactions with in-applicationpurchases. The security of the user device from which the in-applicationtransactions are requested may be verified and attested to. The riskfactors of a given transaction may also be evaluated. A favorable riskscore may result in a transaction moving forward, and an unfavorablerisk score may result in terminating the transaction or a request foradditional authentication. The systems in the present disclosure mayenable communication of sensitive information across a public network tocomplete in-app transactions. Applications of the present disclosure maythus enhance security of digital wallet transactions, enhance the userexperience, and expedite processing.

With reference to FIG. 1 , system 101 for conducting in-applicationtransactions is shown, in accordance with various embodiments. System101 may comprise a user device 100. User device 100 may be any devicecapable of receiving and/or displaying data (e.g., an electronic messagevia public network 140). For example, user device 100 may take the formof a computer or processor, or a set of computers/processors, althoughother types of computing units or systems may be used, includinglaptops, notebooks, hand held computers, personal digital assistants,cellular phones, smart phones (e.g., iPhone®, BlackBerry®, Android®,etc.) tablets, wearables (e.g., smart watches, fitness trackers, andsmart glasses), or any other device capable of receiving data overpublic network 140. Moreover, a user device may not include a physicaldevice, but may include software, data or other ways to receive and/ordisplay information, or software on other devices.

As used herein, the term “network” includes any cloud, cloud computingsystem or electronic communications system or method which incorporateshardware and/or software components. Communication among the parties maybe accomplished through any suitable communication channels, such as,for example, a telephone network, an extranet, an intranet, Internet,point of interaction device (point of sale device, personal digitalassistant (e.g., iPhone®, Blackberry®), cellular phone, kiosk, etc.),online communications, satellite communications, off-linecommunications, wireless communications, transponder communications,local area network (LAN), wide area network (WAN), virtual privatenetwork (VPN), networked or linked devices, keyboard, mouse and/or anysuitable communication or data input modality. Moreover, although thesystem is frequently described herein as being implemented with TCP/IPcommunications protocols, the system may also be implemented using IPX,Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH),or any number of existing or future protocols. If the network is in thenature of a public network, such as the Internet, it may be advantageousto presume the network to be insecure and open to eavesdroppers.Specific information related to the protocols, standards, andapplication software utilized in connection with the Internet isgenerally known to those skilled in the art and, as such, need not bedetailed herein. See, for example, DILIP NAIK, INTERNET STANDARDS ANDPROTOCOLS (1998); JAVA 2 COMPLETE, various authors, (Sybex 1999);DEBORAH RAY AND ERIC RAY, MASTERINO HTML 4.0 (1997); and LOSHIN, TCP/IPCLEARLY EXPLAINED (1997) and DAVID GOURLEY AND BRIAN TOTTY, HTTP, THEDEFINITIVE GUIDE (2002), the contents of which are hereby incorporatedby reference.

A network may be unsecure. Thus, communication over the network mayutilize data encryption. Encryption may be performed by way of any ofthe techniques now available in the art or which may becomeavailable—e.g., Twofish, RSA, AES, El Gamal, Schorr signature, DSA, PGP,PKI, TDEA, ECC, GPG (GnuPG), and symmetric and asymmetric cryptosystems.

In various embodiments, user device 100 may initiate transactions from aweb browser or merchant application. User device 100 may securelycommunicate over public network 140 with wallet provider 110, paymentnetwork 120, and merchant 130 to partially or fully complete thetransactions. With reference to FIG. 2 , system 102 for conductingin-app transactions is shown, in accordance with various embodiments.User device 100 may run a merchant application 104. Merchant applicationmay be provided by merchant 130 and may be made available to users fordownload and execution on user device 100. Merchant application 104 maymake in-application purchases available to a user.

In various embodiments, user device 100 may also comprise a walletprovider client layer 106. Wallet provider client layer 106 may beprovided by wallet provider 110 to enable communication and/orinteraction between merchant application 104 (as well as otherapplications) and a digital wallet on user device 100. In that regard,wallet provider 110 may execute steps on user device 100 via walletprovider client layer 106. A network software development kit 108 (SDK)may also be available on user device 100. The network SDK 108 mayprovide functionality on user device 100 for interaction with paymentnetwork 120 such as, for example, token data parsing, data extractionfrom LUPCs, and/or generation of cryptograms. For example, network SDK108 may return numbers such as an unpredictable number (UN) and/or anapplication transaction counter (ATC) from a limited use paymentcredentials or other session key in response to a function call. The ATCand UN may be used subsequently to authenticate a payment.

In various embodiments, network SDK 108 may be partially or whollyintegrated into a security chip or otherwise integrated into dedicatedhardware located on user device 100. For example, network trusted appmay comprise a trusted execution environment (TEE) on a chip, using chipemulation, and/or both. The TEE may secure sensitive information such asencryption keys and session keys to enhance security of user device 100.Network SDK 108 may provide interface tools with decryption and/orencryption services to securely store LUPCs on user device 100.

In various embodiments, wallet provider 110 may communicate over publicnetwork 140 using wallet provider cloud 112. Wallet provider cloud 112may provide backend services for wallet provider client layer 106 ofuser device 100. Wallet provider cloud 112 may include one or morecomputer or processor, or a set of computers/processors, capable ofreceiving data over public network 140. “Cloud” or “Cloud computing”includes a model for enabling convenient, on-demand network access to ashared pool of configurable computing resources (e.g., networks,servers, storage, applications, and services) that can be rapidlyprovisioned and released with minimal management effort or serviceprovider interaction. A cloud may include one or more servers. Cloudcomputing may include location-independent computing, whereby sharedservers provide resources, software, and data to computers and otherdevices on demand. For more information regarding cloud computing, seethe NIST's (National Institute of Standards and Technology) definitionof cloud computing athttp://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf (lastvisited June 2012), which is hereby incorporated by reference in itsentirety. For example, wallet provider cloud 112 may comprise a networkof servers pooling processing, communication, and storage resources tocomplete in-app transactions.

In various embodiments, the payment network 120 may include paymentnetwork systems 122. Payment network systems 122 may be similar instructure to wallet provider cloud 112 described above. Payment networksystems 122 may provide processing and storage for a transaction accountnetwork. For example, payment network systems 122 may conduct riskassessments on in-app transactions and terminate transactions withunacceptable risk of fraud. Payment network systems 122 may communicatewith credit authorization system 124 (CAS). CAS 124 may provide approvalfor requested transactions that successfully meet the security standardsdisclosed herein. A global authorization network (GAN) 126 may also bein communication with CAS 124. GAN 126 may receive requests frommerchant gateway 134 of merchant 130 and forward requests to CAS 124 forapproval. Merchant 130 may have merchant cloud 132 in communication withmerchant application 104 to provide backend services to merchantapplication 104. Merchant cloud 132 may be similar in structure towallet provider cloud 112 described above.

With reference to FIG. 3 , a process 160 for initiating an in-apptransaction (e.g., purchase) on system 102 is shown, in accordance withvarious embodiments. A user may request an in app purchase using userdevice 100. For example, a user may select an item for purchase andselect a checkout button. Wallet provider client layer 106 is invoked onuser device 100 by passing a transaction date and a transaction amountfrom merchant application 104 to wallet provider client layer 106 inresponse to the user request (Step 162). Wallet provider client layer106 may provide a list of active provisioned cards and/or accounts for auser to pay with. The user may select a card or account and authenticatewith wallet provider 110. Wallet provider 110 may attest whether userdevice 100 is secure (Step 164).

In order to attest that a device is secure, wallet provider 110 maycheck whether user device 100 has been compromised in any way. Forexample, wallet provider 110 may evaluate whether user device 100 hasbeen rooted or jailbroken, has malware or viruses, or is otherwise proneto security breaches. Wallet provider 110 may execute a function call toa security library installed on user device 100 to detect irregularitiesthat ray indicate the user device has been compromised. If walletprovider 110 determined that user device 100 poses an unacceptablesecurity threat then wallet provider 110 may abort the transaction. Insuch an instance, user device 100 may not be used to complete the in-apppurchase.

In various embodiments, wallet provider 110 may get an ATC from the nextlimited use purchase credential (LUPC) and generate a 4-byteunpredictable number (Step 166). The LUPC may be a one-time use key or asession key used to authorize purchases using a digital wallet. Thewallet provider may get an ATC by invoking a function on the network SDK108. Network SDK 108 may comprise an application programming interface(API) with a function (e.g., getTransactionCounter) that, when called bywallet provider client layer 106, returns an ATC. The unpredictablenumber may be at least partially randomly generated on wallet providercloud 112 and may be a hex-encoded, 4-byte number, as detailed in theEMV 4.3 specification available at http://www.emvco.com/default.aspx,which is incorporated by reference herein.

In various embodiments, wallet provider cloud 112 may execute a functionon payment network systems 122 using an API interface to request amodified unpredictable number. In that regard, wallet provider 110invokes the function on payment network systems 122 by passing tokenreference id, the ATC, the unpredictable number (UN), the transactionamount, the transaction date, and other risk assessment variables in anAPI function call (Step 168). The token reference id may identify atoken generated as a surrogate value for a purchase account number andstored on user device 100.

In various embodiments, payment network systems 122 may perform a riskassessment at least partially based on the inputs passed by walletprovider 110 in the function call and other transaction parameters. Therisk assessment may evaluate the values received from wallet provider110 to the expected values or acceptable values. Payment network systems122 may also consider factors such as the age of the token on userdevice 100, the a separate risk assessment by wallet provider 110, theuser's history, the duration the user has been associated with thewallet provider, transaction amount, recent transactions, deviceattributes, device location, or other indicia of trustworthiness. Therisk assessment may return a security code reflective of the risk posedby the transaction. The security code may thus effectively represent arisk score. The security may be used to modify the unpredictable numberusing any binary operator to create the MUN. In that regard, the MUN maystore the state of the risk assessment as the MUN may be the UN encodedwith the security code. The MUN may be generated by the payment networkin advance of an authorization request. The security code and/or the MUNmay be stored against the ATC on CAS 124 (Step 170).

Payment network systems 122 may provide the encrypted MUN to walletprovider cloud 112 (Step 172). Wallet provider 110 may decrypt the MUN,verify the signature and send the MUN to user device 100 (Step 174).Wallet provider client layer 106 may receive the above data from walletprovider cloud 112. Wallet provider client layer 106 may invoke in-apppayment processing using one or more of security code, ATC,unpredictable number. MUN, and/or a session key to generate in-apppayment cryptogram (Step 176).

With reference to FIG. 4 , process 200 for completing an in-app purchaseis shown, in accordance with various embodiments. Wallet provider clientlayer 106 may send a token, token expiry, ATC, unpredictable number,MUN, and/or cryptogram to wallet provider cloud to generate a paymentpayload (Step 202). Wallet provider cloud 112 may generate the paymentpayload by appending the token, token expiry, unpredictable number,MUIN, and/or ATC to the in-app payment cryptogram that was generated inStep 176.

In various embodiments, wallet provider cloud 112 may compute asignature on the payment payload using a private key of wallet provider110 (Step 204). The private key may be an RSA 2048 bit private key thatis 2048 bits long, for example. Other private keys may also be used inplace of an RSA 2048 bit key, including a longer or shorter RSA privatekey or other type of private key used in a suitable asymmetriccryptography protocol. The public key matching the private key may thuslater used to decipher the encrypted data or for signature verification.

In various embodiments, wallet provider cloud 112 may encrypt thepayment payload and its signature using an encryption key (Step 206).The encryption key and algorithm used may be any type of encryption keyknown to those having ordinary skill in the art. The encryption key maybe, for example, random AES 128 bit key. The AES 128 bit key may be asymmetric key to enable decryption with the same key by an intendedrecipient of the AES 128 bit key and encrypted payload. Wallet providercloud 112 may send the encrypted payment payload and signature, as wellas the symmetric encryption key, encrypted by a merchant public key, tomerchant application 104 (Step 208). The merchant public key may bemerchant RSA 3072 bit key, for example. The encrypted signature,encrypted payment payload, and encrypted symmetric encryption key may bedelivered to merchant application 104 by wallet provider client layer106. Merchant application 104 running on user device 100 may send thepayment payload to merchant cloud 132 for decryption with the merchantprivate key (Step 210). The merchant private key may be a RSA 3072 bitkey, for example. After deciphering the wallet provider signature,merchant cloud 132 may verify the signature of the payment payload usingthe wallet provider public key and parse the payment payload (Step 212).The wallet provider public key may be, for example, a RSA 2048 bit key.If the signature is correct the transaction may continue processing.

In various embodiments, parsing the payment payload may includeextracting the token, token expiry, unpredictable number, MUN, ATC,and/or in-app payment cryptogram from the payment payload. The merchantcloud may submit the unpredictable number, the MUN, the ATC, and/or thecryptogram to merchant gateway 134 (Step 214). Merchant gateway 134 mayfurther submit the unpredictable number, the ATC, the cryptogram, andother elements to CAN 126. GAN 126 may send the message to CAS 124 (Step216).

In various embodiments, CAS 124 may compute the in-app paymentcryptogram based on the token, unpredictable number, MUN, ATC, securitycode, and/or session key and approve the transaction if the cryptogramsmatch and the security risk is acceptable (Step 218). CAS 124 may checkeach bit of the calculated in-app payment cryptogram to verify an exactmatch with the cryptogram provided in the payment payload. The riskassessment performed in response to Step 168 may be analyzed at CAS 124to determine whether the transaction possess an acceptable risk prior toissuing an authorization. Risk assessment analysis may be conductedusing the MUN, the security code output from the risk assessment, and/orthe UN. If a transaction poses an unacceptable risk based on the riskassessment CAS 124 may decline the transaction.

With reference to FIGS. 5 and 6A, an exemplary process 260 forcompleting in-application and/or in-browser transactions on system 250is shown, in accordance with various embodiments. Process 600 may besimilar to process 160 and process 200 disclosed above in terms ofpayment payload distribution and encryption. Process 260 may differ fromprocess 160 and process 200 by variation step ordering, as well asvariation in the steps themselves. For example, process 260 may not relyon a modified unpredictable number as disclosed above. System 250 mayalso be similar to system 102 with varying communication structure.

In various embodiments, a user 252 may select an item for purchase onmerchant application 104 and may select checkout (Step 262). Themerchant app may be a native application, a web application, and/or aweb site accessible by user device 100. In that regard, the checkoutexperience may be accessed by user 252 through a web browser.

In various embodiments, merchant application 104 invokes wallet providerclient layer 106, and passes transaction details such as transactionamount, transaction date, and/or transaction currency to wallet providerclient layer 106, in response to user 252 selecting checkout (Step 264).Wallet, provider client layer 106 displays the list of ‘Active’provisioned cards available on user device 100 for user 252 to select acard for payment (Step 266).

In various embodiments, user 252 selects a card and user device 100authenticates with the wallet provider cloud 112 (Step 268). Walletprovider cloud 112 may choose any form of authentication specific towallet provider 110. For example, wallet provider 110 may use passwords,pins, fingerprints, facial recognition, biometrics, and/or othersuitable authentication techniques.

In various embodiments, wallet provider 110 may generate anunpredictable number (Step 270). The unpredictable number may be arandom, hex encoded number. The unpredictable number may have apredetermined length. For example, the unpredictable number may be 4bytes long. The unpredictable number may be used in subsequent steps toenhance transaction security. The unpredictable number may be at leastpartially randomly generated on wallet provider cloud 112 and may be ahex-encoded, 4-byte number, as detailed in the EMV 4.3 specificationavailable at http://www.emvco.com/default.aspx, which is incorporated byreference herein.

In various embodiments, wallet provider client layer 106 may invoke afunction on user device 100 using the unpredictable number (from step270) to calculate an in-app payment cryptogram and retrieve additionaldata including token, token expiry, and/or any token data blocks (Step272). The function may be used to generate an in-app payment cryptogramfor processing an in-application or in-browser transaction. An in-apppayment cryptogram may be calculated using the unpredictable number, anATC (retrieved from an LUPC), and card verification results (CVR). Thus,the in-app payment cryptogram may be an 8 byte cryptogram including theunpredictable number, the ATC, and/or the CVR. A token data block mayinclude a cryptogram reference ID, the in-app cryptogram, theunpredictable number, the ATC, the CVR, a derivation key index (DKI,also retrieved from an LUPC), a primary account number (PAN) sequence,and/or a predetermined number of hex 0s. For example, a first token datablock may include a cryptogram reference ID, the in-app cryptogram,unpredictable number, ATC, CVR, DKI, PAN sequence and have a totallength of 20 bytes. A second token data block may include 20 bytes ofhex 0s. A DKI may comprise data for identifying a derivation key. Thederivation key may be used in deriving a master key, for example. Walletprovider 110 (using wallet provider client layer 106 and/or walletprovider cloud 112) may also generate a payment payload by appending thetoken, token expiry, unpredictable number, and/or ATC to the in-apppayment cryptogram that was generated in step 272.

In various embodiments, wallet provider client layer 106 may provide thetoken, token expiry, and/or token data blocks (from step 272) tomerchant application 104 running on user device 100 (Step 274). Thetoken data blocks include the in-app payment cryptogram calculated instep 272 for later comparison to a separately generated paymentcryptogram. Merchant application 104 may transmit the token, tokenexpiry, and/or token data blocks (from step 274) to merchant cloud 132(Step 276).

Continuing with reference to FIGS. 5 and 6B, merchant cloud 132 maysubmit the token, token expiry, and/or token data blocks along withother payment attributes such as a payment payload to merchant gateway134 (Step 278). Merchant gateway 134 may submit the transaction to theglobal authorization network 126 (Step 280). Payment network 120 maycompute the payment cryptogram and compare the computed paymentcryptogram to the in-app payment cryptogram. Payment network 120 mayapprove the transaction, in response to the cryptogram matching and arisk assessment passing (Step 282).

In various embodiments, payment network systems 122 may perform the riskassessment at least partially based on the token, token expiry,cryptogram reference ID, the in-app cryptogram, the unpredictablenumber, the ATC, the CVR, a derivation key index (DKI), a primaryaccount number (PAN) sequence, transaction amount, transaction location,and/or other transaction parameters. The risk assessment may compare thevalues received to expected values and/or acceptable values. Paymentnetwork systems 122 may also consider factors such as the age of thetoken on user device 100, the separate risk assessment by walletprovider 110, the user's history, the duration the user has beenassociated with the wallet provider, transaction amount, recenttransactions, device attributes, device location, and/or other indiciaof trustworthiness. The risk assessment may return a security codereflective of the risk posed by the transaction. The security code maythus effectively represent a risk score.

In various embodiments, payment network 120 may request that user device100 refresh the LUPCs on user device 100, in response to risk assessmentresults (Step 284). The request may be issued after authorizing and/ordeclining a transaction. A refresh request may impact future in-apptransactions by increasing the risk threshold for approval in responseto a pre-refresh LUPC being used. For example, a transaction of $1.50may be approved using an old LUPC after a refresh request, but a $20.00transaction may be declined using the old LUPC. Payment network systems122 may direct wallet provider cloud 112 to refresh LUPCs (Step 286).

In various embodiments, wallet provider cloud 112 may complete deviceattestation of user device 100 and, on successful attestation, invokewallet provider to complete device attestation (Step 288. In order toattest that a device is secure, as disclosed above, wallet provider 110may check whether user device 100 has been compromised in any way. Forexample, wallet provider 110 may evaluate whether user device 100 hasbeen rooted or jailbroken, has malware or viruses, or is otherwise proneto security breaches. Wallet provider 110 may execute a function call toa security library installed on user device 100 to detect irregularitiesthat may indicate the user device 100 has been compromised. If walletprovider 110 determined that user device 100 poses an unacceptablesecurity threat wallet provider 110 may abort the LUPC refresh.

In various embodiments, payment network 120 may conduct a risk analysisand, depending on the outcome, provide refreshed LUPCs and/or reject theLUPC request (Step 290). For example, if the risk analysis indicates ahigh risk, payment network 120 may reject the request. If the walletprovider client layer 106 does not receive the updated LUPC, then futurein-application and/or in-browser purchases may be declined, as theexisting LUPC may be recognized as no longer valid for completing in-apptransactions. In-app transactions may thus be frozen in response to LUPCrefresh failing. Wallet provider 110 may provide retry parameters toupdate LUPCs securely at a later time (Step 292). In that regard, LUPCupdates may be approved or denied based on device attestation and riskassessment. Payment network 120 may effectively force wallet provider110 and/or user device 100 to complete device attestation in order torefresh LUPCs and continue using the in-application or in-browsertransaction system.

As used herein, “match” or “associated with” or similar phrases mayinclude an identical match, a partial match, meeting certain criteria,matching a subset of data, a correlation, satisfying certain criteria, acorrespondence, an association, an algorithmic relationship and/or thelike. Similarly, as used herein, “authenticate” or similar terms mayinclude an exact authentication, a partial authentication,authenticating a subset of data, a correspondence, satisfying certaincriteria, an association, an algorithmic relationship and/or the like.

Any communication, transmission and/or channel discussed herein mayinclude any system or method for delivering content (e.g. data,information, metadata, etc.), and/or the content itself. The content maybe presented in any form or medium, and in various embodiments, thecontent may be delivered electronically and/or capable of beingpresented electronically. For example, a channel may comprise a websiteor device (e.g., Facebook, YOUTUBE®, APPLE®TV®, PANDORA®, XBOX®, SONY®,PLAYSTATION®), a uniform resource locator (“URL”), a document (e.g., aMICROSOFT®, Word® document, a MICROSOFT® Excel® document, an ADOBE® .pdfdocument, etc.), an “ebook,” an “emagazine,” an application ormicroapplication (as described herein), an SMS or other type of textmessage, an email, facebook, twitter, MMS and/or other type ofcommunication technology. In various embodiments, a channel may behosted or provided by a data partner. In various embodiments, thedistribution channel may comprise at least one of a merchant website, asocial media website, affiliate or partner websites, an external vendor,a mobile device communication, social media network and/or locationbased service. Distribution channels may include at least one of amerchant website, a social media site, affiliate or partner websites, anexternal vendor, and a mobile device communication. Examples of socialmedia sites include FACEBOOK®, FOURSQUARE®, TWITTER®, MYSPACE®,LINKEDIN®, and the like. Examples of affiliate or partner websitesinclude AMERICAN EXPRESS®, GROUPON®, LIVINGSOCIAL®, and the like.Moreover, examples of mobile device communications include texting,email, and mobile applications for smartphones.

The phrases consumer, customer, user, transaction account holder, cardmember or the like shall include any person, entity, business,government organization, business, software, hardware, machineassociated with a transaction account, buys merchant offerings offeredby one or more merchants using the account and/or who is legallydesignated for performing transactions on the account, regardless ofwhether a physical card is associated with the account. For example, thecard member may include a transaction account owner, a transactionaccount user, an account affiliate, a child account user, a subsidiaryaccount user, a beneficiary of an account, a custodian of an account,and/or any other person or entity affiliated or associated with atransaction account.

In various embodiments, the methods described herein are implementedusing the various particular machines described herein. The methodsdescribed herein may be implemented using the below particular machines,and those hereinafter developed, in any suitable combination, as wouldbe appreciated immediately by one skilled in the art. Further, as isunambiguous from this disclosure, the methods described herein mayresult in various transformations of certain articles.

For the sake of brevity, conventional data networking, applicationdevelopment and other functional aspects of the systems (and componentsof the individual operating components of the systems) may not bedescribed in detail herein. Furthermore, the connecting lines shown inthe various figures contained herein are intended to represent exemplaryfunctional relationships and/or physical couplings between the variouselements. It should be noted that many alternative or additionalfunctional relationships or physical connections may be present in apractical system.

The various system components discussed herein may include one or moreof the following: a host server or other computing systems including aprocessor for processing digital data; a memory coupled to the processorfor storing digital data; an input digitizer coupled to the processorfor inputting digital data; an application program stored in the memoryand accessible by the processor for directing processing of digital databy the processor; a display device coupled to the processor and memoryfor displaying information derived from digital data processed by theprocessor; and a plurality of databases. Various databases used hereinmay include: client data; merchant data; financial institution data;and/or like data useful in the operation of the system. As those skilledin the art will appreciate, user computer may include an operatingsystem (e.g., WINDOWS® NT®, WINDOWS® 95/98/2000®, WINDOWS® XP®, WINDOWS®Vista®, WINDOWS® 7®, OS2, UNIX®, LINUX®, SOLARIS®. MacOS, etc.) as wellas various conventional support software and drivers typicallyassociated with computers.

The present system or any part(s) or function(s) thereof may beimplemented using hardware, software or a combination thereof and may beimplemented in one or more computer systems or other processing systems.However, the manipulations performed by embodiments were often referredto in terms, such as matching or selecting, which are commonlyassociated with mental operations performed by a human operator. No suchcapability of a human operator is necessary, or desirable in most cases,in any of the operations described herein. Rather, the operations may bemachine operations. Useful machines for performing the variousembodiments include general purpose digital computers or similardevices.

In fact, in various embodiments, the embodiments are directed toward oneor more computer systems capable of carrying out the functionalitydescribed herein. The computer system includes one or more processors,such as processor. The processor is connected to a communicationinfrastructure (e.g., a communications bus, cross over bar, or network).Various software embodiments are described in term of this exemplarycomputer system. After reading this description, it will become apparentto a person skilled in the relevant art(s) how to implement variousembodiments using other computer systems and/or architectures. Computersystem can include a display interface that forwards graphics, text, andother data from the communication infrastructure (or from a frame buffernot shown) for display on a display unit.

Computer system also includes a main memory, such as for example randomaccess memory (RAM), and may also include a secondary memory. Thesecondary memory may include, for example, a hard disk drive and/or aremovable storage drive, representing a floppy disk drive, a magnetictape drive, an optical disk drive, etc. The removable storage drivereads from and/or writes to a removable storage unit in a well-knownmanner. Removable storage unit represents a floppy disk, magnetic tape,optical disk, etc. which is read by and written to by removable storagedrive. As will be appreciated, the removable storage unit includes acomputer usable storage medium having stored therein computer softwareand/or data.

In various embodiments, secondary memory may include other similardevices for allowing computer programs or other instructions to beloaded into computer system. Such devices may include, for example, aremovable storage unit and an interface. Examples of such may include aprogram cartridge and cartridge interface (such as that found in videogame devices), a removable memory chip (such as an erasable programmableread only memory (EPROM), or programmable read only memory (PROM)) andassociated socket, and other removable storage units and interfaces,which allow software and data to be transferred from the removablestorage unit to computer system.

Computer system may also include a communications interface.Communications interface allows software and data to be transferredbetween computer system and external devices. Examples of communicationsinterface may include a modem, a network interface (such as an Ethernetaccount), a communications port, a Personal Computer Memory AccountInternational Association (PCMCIA) slot and account, etc. Software anddata transferred via communications interface are in the form of signalswhich may be electronic, electromagnetic, optical or other signalscapable of being received by communications interface. These signals areprovided to communications interface via a communications path (e.g.,channel). This channel carries signals and may be implemented usingwire, cable, fiber optics, a telephone line, a cellular link, a radiofrequency (RF) link, wireless and other communications channels.

The terms “computer program medium” and “computer usable medium” and“computer readable medium” are used to generally refer to media such asremovable storage drive and a hard disk installed in hard disk drive.These computer program products provide software to computer system.

Computer programs (also referred to as computer control logic) arestored in main memory and/or secondary memory. Computer programs mayalso be received via communications interface. Such computer programs,when executed, enable the computer system to perform the features asdiscussed herein. In particular, the computer programs, when executed,enable the processor to perform the features of various embodiments.Accordingly, such computer programs represent controllers of thecomputer system.

In various embodiments, software may be stored in a computer programproduct and loaded into computer system using removable storage drive,hard disk drive or communications interface. The control logic(software), when executed by the processor, causes the processor toperform the functions of various embodiments as described herein. Invarious embodiments, hardware components such as application specificintegrated circuits (ASICs). Implementation of the hardware statemachine so as to perform the functions described herein will be apparentto persons skilled in the relevant art(s).

In various embodiments, the server may include application servers (e.g.WEB SPHERE, WEB LOGIC, and JBOSS). In various embodiments, the servermay include web servers (e.g. APACHE, IIS, GWS, SUN JAVA® SYSTEM WEBSERVER).

A web client includes any device (e.g., personal computer) whichcommunicates via any network, for example such as those discussedherein. Such browser applications comprise Internet browsing softwareinstalled within a computing unit or a system to conduct onlinetransactions and/or communications. These computing units or systems maytake the form of a computer or set of computers, although other types ofcomputing units or systems may be used, including laptops, notebooks,tablets, hand held computers, personal digital assistants, set-topboxes, workstations, computer-servers, main frame computers,mini-computers, PC servers, pervasive computers, network sets ofcomputers, personal computers, such as IPADS®, IMACS®, and MACBOOKS®,kiosks, terminals, point of sale (POS) devices and/or terminals,televisions, or any other device capable of receiving data over anetwork. A web-client may run MICROSOFT® INTERNET EXPLORER®, MOZILLA®FIREFOX®, GOOGLE® CHROME®, APPLE® Safari, or any other of the myriadsoftware packages available for browsing the internet.

Practitioners will appreciate that a web client may or may not be indirect contact with an application server. For example, a web client mayaccess the services of an application server through another serverand/or hardware component, which may have a direct or indirectconnection to an Internet server. For example, a web client maycommunicate with an application server via a load balancer. In variousembodiments, access is through a network or the Internet through acommercially-available web-browser software package.

As those skilled in the art will appreciate, a web client includes anoperating system (e.g., WINDOWS® NT), 95/98/2000/CE/Mobile, OS2, UNIX®,LINUX®, SOLARIS®, MacOS, etc.) as well as various conventional supportsoftware and drivers typically associated with computers. A web clientmay include any suitable personal computer, network computer,workstation, personal digital assistant, cellular phone, smart phone,minicomputer, mainframe or the like. A web client can be in a home orbusiness environment with access to a network. In various embodiments,access is through a network or the Internet through a commerciallyavailable web-browser software package. A web client may implementsecurity protocols such as Secure Sockets Layer (SSL) and TransportLayer Security (TLS). A web client may implement several applicationlayer protocols including http, https, ftp, and sftp.

In various embodiments, components, modules, and/or engines of system102 may be implemented as micro-applications or micro-apps. Micro-appsare typically deployed in the context of a mobile operating system,including for example, a WINDOWS® mobile operating system, an ANDROID®Operating System, APPLE® IOS®, a BLACKBERRY® operating system and thelike. The micro-app may be configured to leverage tie resources of thelarger operating system and associated hardware via a set ofpredetermined rules which govern the operations of various operatingsystems and hardware resources. For example, where a micro-app desiresto communicate with a device or network other than the mobile device ormobile operating system, the micro-app may leverage the communicationprotocol of the operating system and associated device hardware underthe predetermined rules of the mobile operating system. Moreover, wherethe micro-app desires an input from a user, the micro-app may beconfigured to request a response from the operating system whichmonitors various hardware components and then communicates a detectedinput from the hardware to the micro-app.

The various system components may be independently, separately orcollectively suitably coupled to the network via data links whichincludes, for example, a connection to an Internet Service Provider(ISP) over the local loop as is typically used in connection withstandard modem communication, cable modem, Dish Networks®, ISDN, DigitalSubscriber Line (DSL), or various wireless communication methods, see,e.g., GILBERT HELD, UNDERSTANDING DATA COMMUNICATIONS (1996), which ishereby incorporated by reference. It is noted that the network may beimplemented as other types of networks, such as an interactivetelevision (ITV) network. Moreover, the system contemplates the use,sale or distribution of any goods, services or information over anynetwork having similar functionality described herein.

As used herein, “transmit” may include sending electronic data from onesystem component to another over a network connection. Additionally, asused herein, “data” may include encompassing information such ascommands, queries, files, data for storage, and the like in digital orany other form.

The system contemplates uses in association with web services, utilitycomputing, pervasive and individualized computing, security and identitysolutions, autonomic computing, cloud computing, commodity computing,mobility and wireless solutions, open source, biometrics, grid computingand/or mesh computing.

Any databases discussed herein may include relational, hierarchical,graphical, or object-oriented structure and/or any other databaseconfigurations. Common database products that may be used to implementthe databases include DB2 by IBM® (Armonk, N.Y.), various databaseproducts available from ORACLE® Corporation (Redwood Shores, Calif.),MICROSOFT® Access® or MICROSOFT® SQL Server® by MICROSOFT® Corporation(Redmond, Wash.), MySQL by MySQL AB (Uppsala, Sweden), or any othersuitable database product. Moreover, the databases may be organized inany suitable manner, for example, as data tables or lookup tables. Eachrecord may be a single file, a series of files, a linked series of datafields or any other data structure. Association of certain data may beaccomplished through any desired data association technique such asthose known or practiced in the art. For example, the association may beaccomplished either manually or automatically. Automatic associationtechniques may include, for example, a database search, a databasemerge, GREP, AGREP, SQL, using a key field in the tables to speedsearches, sequential searches through all the tables and files, sortingrecords in the file according to a known order to simplify lookup,and/or the like. The association step may be accomplished by a databasemerge function, for example, using a “key field” in pre-selecteddatabases or data sectors. Various database tuning steps arecontemplated to optimize database performance. For example, frequentlyused files such as indexes may be placed on separate file systems toreduce In/Out (“I/O”) bottlenecks.

One skilled in the art will also appreciate that, for security reasons,any databases, systems, devices, servers or other components of thesystem may consist of any combination thereof at a single location or atmultiple locations, wherein each database or system includes any ofvarious suitable security features, such as firewalls, access codes,encryption, decryption, compression, decompression, and/or the like.

The computers discussed herein may provide a suitable website or otherInternet-based graphical user interface which is accessible by users. Inone embodiment, the MICROSOFT® INTERNET INFORMATION SERVICES® (IIS),MICROSOFT® Transaction Server (MTS), and MICROSOFT® SQL Server, are usedin conjunction with the MICROSOFT® operating system, MICROSOFT® NT webserver software, a MICROSOFT® SQL Server database system, and aMICROSOFT® Commerce Server. Additionally, components such as Access orMICROSOFT® SQL Server, ORACLE®, Sybase, Informix MySQL, Interbase, etc.,may be used to provide an Active Data Object (ADO) compliant databasemanagement system. In one embodiment, the Apache web server is used inconjunction with a Linux operating system, a MySQL database, and thePerl, PHP, and/or Python programming languages.

Any of the communications, inputs, storage, databases or displaysdiscussed herein may be facilitated through a website having web pages.The term “web page” as it is used herein is not meant to limit the typeof documents and applications that might be used to interact with theuser. For example, a typical website might include, in addition tostandard HTML documents, various forms, JAVA® APPLE®ts, JAVASCRIPT,active server pages (ASP), common gateway interface scripts (COI),extensible markup language (XML), dynamic HTML, cascading style sheets(CSS), AJAX (Asynchronous JAVASCRIPT And XML), helper applications,plug-ins, and the like. A server may include a web service that receivesa request from a web server, the request including a URL and an IPaddress (123.56.789.234). The web server retrieves the appropriate webpages and sends the data or applications for the web pages to the IPaddress. Web services are applications that are capable of interactingwith other applications over a communications means, such as theinternet. Web services are typically based on standards or protocolssuch as XML, SOAP, AJAX, WSDL and UDDI. Web services methods are wellknown in the art, and are covered in many standard texts. See, e.g.,ALEX NGHIEM, IT WEB SERVICES: A ROADMAP FOR THE ENTERPRISE (2003),hereby incorporated by reference.

Middleware may include any hardware and/or software suitably configuredto facilitate communications and/or process transactions betweendisparate computing systems. Middleware components are commerciallyavailable and known in the art. Middleware may be implemented throughcommercially available hardware and/or software, through custom hardwareand/or software components, or through a combination thereof. Middlewaremay reside in a variety of configurations and may exist as a standalonesystem or may be a software component residing on the Internet server.Middleware may be configured to process transactions between the variouscomponents of an application server and any number of internal orexternal systems for any of the purposes disclosed herein. WEBSPHERE MQ™(formerly MQSeries) by IBM®, Inc. (Armonk, N.Y.) is an example of acommercially available middleware product. An Enterprise Service Bus(“ESB”) application is another example of middleware.

Practitioners will also appreciate that there are a number of methodsfor displaying data within a browser-based document. Data may berepresented as standard text or within a fixed list, scrollable list,drop-down list, editable text field, fixed text field, pop-up window,and the like. Likewise, there are a number of methods available formodifying data in a web page such as, for example, free text entry usinga keyboard, selection of menu items, check boxes, option boxes, and thelike.

The system and method may be described herein in terms of functionalblock components, screen shots, optional selections and variousprocessing steps. It should be appreciated that such functional blocksmay be realized by any number of hardware and/or software componentsconfigured to perform the specified functions. For example, the systemmay employ various integrated circuit components, e.g., memory elements,processing elements, logic elements, look-up tables, and the like, whichmay carry out a variety of functions under the control of one or moremicroprocessors or other control devices. Similarly, the softwareelements of the system may be implemented with any programming orscripting language such as C, C++, C#, JAVA®, JAVASCRIPT, VBScript,Macromedia Cold Fusion, COBOL, MICROSOFT® Active Server Pages, assembly,PERL, PHP, awk, Python, Visual Basic, SQL Stored Procedures, PL/SQL, anyUNIX shell script, and extensible markup language (XML) with the variousalgorithms being implemented with any combination of data structures,objects, processes, routines or other programming elements. Further, itshould be noted that the system may employ any number of conventionaltechniques for data transmission, signaling, data processing, networkcontrol, and the like. Still further, the system could be used to detector prevent security issues with a client-side scripting language, suchas JAVASCRIPT, VBScript or the like. For a basic introduction ofcryptography and network security, see any of the following references:(1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,”by Bruce Schneier, published by John Wiley & Sons (second edition,1995); (2) “JAVA® Cryptography” by Jonathan Knudson, published byO'Reilly & Associates (1998); (3) “Cryptography & Network Security:Principles & Practice” by William Stallings, published by Prentice Hall;all of which are hereby incorporated by reference.

As used herein, the term “end user”, “consumer”, “customer”, “accountmember”, “business” or “merchant” may be used interchangeably with eachother, and each shall mean any person, entity, government organization,business, machine, hardware, and/or software. A bank may be part of thesystem, but the bank may represent other types of account issuinginstitutions, such as credit account companies, account sponsoringcompanies, or third party issuers under contract with financialinstitutions. It is further noted that other participants may beinvolved in some phases of the transaction, such as an intermediarysettlement institution, but these participants are not shown.

As will be appreciated by one of ordinary skill in the art, the systemmay be embodied as a customization of an existing system, an add-onproduct, a processing apparatus executing upgraded software, astandalone system, a distributed system, a method, a data processingsystem, a device for data processing, and/or a computer program product.Accordingly, any portion of the system or a module may take the form ofa processing apparatus executing code, an internet based embodiment, anentirely hardware embodiment, or an embodiment combining aspects of theinternet, software and hardware. Furthermore, the system may take theform of a computer program product on a computer-readable storage mediumhaving computer-readable program code means embodied in the storagemedium. Any suitable computer-readable storage medium may be utilized,including hard disks, CD-ROM, optical storage devices, magnetic storagedevices, and/or the like.

The system and method is described herein with reference to screenshots, block diagrams and flowchart illustrations of methods, apparatus(e.g., systems), and computer program products according to variousembodiments. It will be understood that each functional block of theblock diagrams and the flowchart illustrations, and combinations offunctional blocks in the block diagrams and flowchart illustrations,respectively, can be implemented by computer program instructions.

These computer program instructions may be loaded onto a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructionsthat execute on the computer or other programmable data processingapparatus create means for implementing the functions specified in theflowchart block or blocks. These computer program instructions may alsobe stored in a computer-readable memory that, can direct a computer orother programmable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function specified in the flowchart block or blocks.The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flowchartillustrations support combinations of means for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instruction means for performing the specified functions. Itwill also be understood that each functional block of the block diagramsand flowchart illustrations, and combinations of functional blocks inthe block diagrams and flowchart illustrations, can be implemented byeither special purpose hardware-based computer systems which perform thespecified functions or steps, or suitable combinations of specialpurpose hardware and computer instructions. Further, illustrations ofthe process flows and the descriptions thereof may make reference touser WINDOWS®, webpages, websites, web forms, prompts, etc.Practitioners will appreciate that the illustrated steps describedherein may comprise in any number of configurations including the use ofWINDOWS®, webpages, web forms, popup WINDOWS®, prompts and the like. Itshould be further appreciated that the multiple steps as illustrated anddescribed may be combined into single webpages and/or WINDOWS® but havebeen expanded for the sake of simplicity. In other cases, stepsillustrated and described as single process steps may be separated intomultiple webpages and/or WINDOWS® but have been combined for simplicity.

The term “non-transitory” is to be understood to remove only propagatingtransitory signals per se from the claim scope and does not relinquishrights to all standard computer-readable media that are not onlypropagating transitory signals per se. Stated another way, the meaningof the term “non-transitory computer-readable medium” and“non-transitory computer-readable storage medium” should be construed toexclude only those types of transitory computer-readable media whichwere found in In Re Nuijten to fall outside the scope of patentablesubject matter under 35 U.S.C. § 101.

Phrases and terms similar to “account”, “account number”, “account code”or “consumer account” as used herein, may include any device, code(e.g., one or more of an authorization/access code, personalidentification number (“PIN”). Internet code, other identification code,and/or the like), number, letter, symbol, digital certificate, smartchip, digital signal, analog signal, biometric or otheridentifier/indicia suitably configured to allow the consumer to access,interact with or communicate with the system. The account number mayoptionally be located on or associated with a rewards account, chargeaccount, credit account, debit account, prepaid account, telephoneaccount, embossed account, smart account, magnetic stripe account, barcode account, transponder, radio frequency account or an associatedaccount.

The system may include or interface with any of the foregoing accounts,devices, and/or a transponder and reader (e.g. RFID reader) in RFcommunication with the transponder (which may include a fob), orcommunications between an initiator and a target enabled by near fieldcommunications (NFC). Typical devices may include, for example, a keyring, tag, account, cell phone, wristwatch or any such form capable ofbeing presented for interrogation. Moreover, the system, computing unitor device discussed herein may include a “pervasive computing device,”which may include a traditionally non-computerized device that isembedded with a computing unit. Examples may include watches, Internetenabled kitchen appliances, restaurant tables embedded with RF readers,wallets or purses with imbedded transponders, etc. Furthermore, a deviceor financial transaction instrument may have electronic andcommunications functionality enabled, for example, by: a network ofelectronic circuitry that is printed or otherwise incorporated onto orwithin the transaction instrument (and typically referred to as a “smartaccount”); a fob having a transponder and an RFID reader; and/or nearfield communication (NFC) technologies. For more information regardingNFC, refer to the following specifications all of which are incorporatedby reference herein: ISO/IEC 18092/ECMA-340, Near Field CommunicationInterface and Protocol-1 (NFCIP-1); ISO/IEC 21481/ECMA-352, Near FieldCommunication Interface and Protocol-2 (NFCIP-2); and EMV 4.3 availableat http://www.emvco.com/default.aspx.

The account number may be distributed and stored in any form of plastic,electronic, magnetic, radio frequency, wireless, audio and/or opticaldevice capable of transmitting or downloading data from itself to asecond device. A consumer account number may be, for example, asixteen-digit account number, although each credit provider has its ownnumbering system, such as the fifteen-digit numbering system used byAmerican Express. Each company's account numbers comply with thatcompany's standardized format such that the company using afifteen-digit format will generally use three-spaced sets of numbers, asrepresented by the number “0000 000000 00000”. The first five to sevendigits are reserved for processing purposes and identify the issuingbank, account type, etc. In this example, the last (fifteenth) digit isused as a sum check for the fifteen digit number. The intermediaryeight-to-eleven digits are used to uniquely identify the consumer. Amerchant account number may be, for example, any number or alpha-numericcharacters that identify a particular merchant for purposes of accountacceptance, account reconciliation, reporting, or the like.

In various embodiments, an account number may identify a consumer. Inaddition, in various embodiments, a consumer may be identified by avariety of identifiers, including, for example, an email address, atelephone number, a cookie id, a radio frequency identifier (RFID), abiometric, a motion, a measurement and/or the like.

Phrases and terms similar to “transaction account” may include anyaccount that may be used to facilitate a financial transaction.

Phrases and terms similar to “financial institution” or “transactionaccount issuer” may include any entity that offers transaction accountservices. Although often referred to as a “financial institution,” thefinancial institution may represent any type of bank, lender or othertype of account issuing institution, such as credit account companies,account sponsoring companies, or third party issuers under contract withfinancial institutions. It is further noted that other participants maybe involved in some phases of the transaction, such as an intermediarysettlement institution.

Phrases and terms similar to “internal data” may include any data acredit issuer possesses or acquires pertaining to a particular consumer.Internal data may be gathered before, during, or after a relationshipbetween die credit issuer and the transaction account holder (e.g., theconsumer or buyer). Such data may include consumer demographic data.Consumer demographic data includes any data pertaining to a consumer.Consumer demographic data may include consumer name, address, telephonenumber, email address, employer and social security number. Consumertransactional data is any data pertaining to the particular transactionsin which a consumer engages during any given time period. Consumertransactional data may include, for example, transaction amount,transaction date, transaction vendor/merchant, and transactionvendor/merchant location.

Transaction vendor/merchant location may contain a high degree ofspecificity to a vendor/merchant. For example, transactionvendor/merchant location may include a particular gasoline filingstation in a particular postal code located at a particular crosssection or address. Also, for example, transaction vendor/merchantlocation may include a particular web address, such as a UniformResource Locator (“URL”), an email address and/or an Internet Protocol(“IP”) address for a vendor/merchant. Transaction vendor/merchant andtransaction vendor/merchant location may be associated with a particularconsumer and further associated with sets of consumers. Consumer paymentdata includes any data pertaining to a consumer's history of paying debtobligations. Consumer payment data may include consumer payment dates,payment amounts, balance amount, and credit limit Internal data mayfurther comprise records of consumer service calls, complaints, requestsfor credit line increases, questions, and comments. A record of aconsumer service call includes, for example, date of call, reason forcall, and any transcript or summary of the actual call.

Systems, methods and computer program products are provided. In thedetailed description herein, references to “various embodiments”, “oneembodiment”, “an embodiment”, “an example embodiment”, etc., indicatethat the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to affect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described. After reading the description, itwill be apparent to one skilled in the relevant art(s) how to implementthe disclosure in alternative embodiments.

Benefits, other advantages, and solutions to problems have beendescribed herein with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any elements that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as critical, required, or essentialfeatures or elements of the disclosure. The scope of the disclosure isaccordingly to be limited by nothing other than the appended claims, inwhich reference to an element in the singular is not intended to mean“one and only one” unless explicitly so stated, but rather “one ormore.” Moreover, where a phrase similar to ‘at least one of A, B, and C’or ‘at least one of A, B, or C’ is used in the claims or specification,it is intended that the phrase be interpreted to mean that A alone maybe present in an embodiment, B alone may be present in an embodiment, Calone may be present in an embodiment, or that any combination of theelements A, B and C may be present in a single embodiment; for example,A and B, A and C, B and C, or A and B and C. Although the disclosureincludes a method, it is contemplated that it may be embodied ascomputer program instructions on a tangible computer-readable carrier,such as a magnetic or optical memory or a magnetic or optical disk. Allstructural, chemical, and functional equivalents to the elements of theabove-described exemplary embodiments that are known to those ofordinary skill in the art are expressly incorporated herein by referenceand are intended to be encompassed by the present claims. Moreover, itis not necessary for a device or method to address each and everyproblem sought to be solved by the present disclosure, for it to beencompassed by the present claims.

Furthermore, no element, component, or method step in the presentdisclosure is intended to be dedicated to the public regardless ofwhether the element, component, or method step is explicitly recited inthe claims. No claim element herein is to be construed under theprovisions of 35 U.S.C. 112 (f) unless the element is expressly recitedusing the phrase “means for.” As used herein, the terms “comprises”,“comprising”, or any other variation thereof, are intended to cover anon-exclusive inclusion, such that a process, method, article, orapparatus that comprises a list of elements does not include only thoseelements but may include other elements not expressly listed or inherentto such process, method, article, or apparatus.

Therefore, the following is claimed:
 1. A method comprising:identifying, by a client device, a purchase transaction request from amerchant application executed on the client device; generating, by theclient device, an in-app payment cryptogram for the purchase transactionrequest based at least in part on a limited use payment credential(LUPC); providing, by the client device, the in-app payment cryptogramto the merchant application, wherein the merchant application transmitsthe in-app payment cryptogram to a merchant computing device; receiving,by the client device, a request from a payment network associated withthe merchant computing device to update the LUPC; determining, by theclient device, that the client device is secure by executing a securitylibrary stored in the client device in response to receiving the requestto update the LUPC, wherein the execution of the security librarygenerates a device attestation response, and the device attestationresponse is transmitted to the payment network; and receiving, by theclient device, an updated LUPC from the payment network.
 2. The methodof claim 1, further comprising: identifying, by the client device, aselection of a payment instrument from a digital wallet; andtransmitting, by the client device, the selection of the paymentinstrument to a wallet service provider for the purchase transactionrequest.
 3. The method of claim 2, further comprising: transmitting, bythe client device, to the wallet service provider a user credential forauthentication of the payment instrument; and receiving, by the clientdevice, transaction security data from the wallet service provider inresponse to authentication of the payment instrument.
 4. The method ofclaim 3, wherein the transaction security data comprises anunpredictable number generated by the wallet service provider, whereinthe LUPC is generated based at least in part on the unpredictablenumber.
 5. The method of claim 2, wherein providing the in-app paymentcryptogram to the merchant application further comprises providing atoken associated with the payment instrument to the merchantapplication.
 6. The method of claim 1, wherein the merchant applicationcomprises at least one of a browser application, a native application, aweb application, or a web site executed on the client device.
 7. Themethod of claim 1, wherein the LUPC is a session key configured toauthorize a purchase using a digital wallet on the client device.
 8. Asystem, comprising: a computing device that includes a processor; and amemory storing instructions, that when executed by the processor, causethe computing device to perform at least operations of: identifying apurchase transaction request from a merchant application executed on thecomputing device; generating an in-app payment cryptogram for thepurchase transaction request based at least in part on a limited usepayment credential (LUPC); providing the in-app payment cryptogram tothe merchant application, wherein the merchant application transmits thein-app payment cryptogram to a merchant computing device; receiving arequest from a payment network associated with the merchant computingdevice to update the LUPC; determining that the computing device issecure by executing a security library stored in the computing device inresponse to receiving the request to update the LUPC, wherein theexecution of the security library generates a device attestationresponse, and the device attestation response is transmitted to thepayment network; and receiving an updated LUPC from the payment network.9. The system of claim 8, wherein the instructions, when executed by theprocessor, further cause the computing device to perform at least theoperations of: identifying a selection of a payment instrument from adigital wallet; and transmitting the selection of the payment instrumentto a wallet service provider for the purchase transaction request. 10.The system of claim 9, wherein the instructions, when executed by theprocessor, further cause the computing device to perform at least theoperations of: transmitting to the wallet service provider a usercredential for authentication of the payment instrument; and receivingtransaction security data from the wallet service provider in responseto authentication of the payment instrument.
 11. The system of claim 10,wherein the transaction security data comprises an unpredictable numbergenerated by the wallet service provider, wherein the LUPC is generatedbased at least in part on the unpredictable number.
 12. The system ofclaim 8, wherein the instructions, when executed by the processor, causethe computing device to perform the providing of the in-app paymentcryptogram to the merchant application which further cause the computingdevice to perform at least the operation of providing a token associatedwith a payment instrument to the merchant application.
 13. The system ofclaim 8, wherein the merchant application comprises at least one of abrowser application, a native application, a web application, or a website executed on the computing device.
 14. The system of claim 8,wherein the LUPC is a session key configured to authorize a purchaseusing a digital wallet on the computing device.
 15. A non-transitorycomputer-readable medium embodying machine-executable instructionsstored thereon that, when executed by a processor of a computing device,cause the computing device to perform at least operations of:identifying a purchase transaction request from a merchant applicationexecuted on the computing device; generating an in-app paymentcryptogram for the purchase transaction request based at least in parton a limited use payment credential (LUPC); providing the in-app paymentcryptogram to the merchant application, wherein the merchant applicationtransmits the in-app payment cryptogram to a merchant computing device;receiving a request from a payment network associated with the merchantcomputing device to update the LUPC; determining that the computingdevice is secure by executing a security library stored in the computingdevice in response to receiving the request to update the LUPC, whereinthe execution of the security library generates a device attestationresponse, and the device attestation response is transmitted to thepayment network; and receiving an updated LUPC from the payment network.16. The non-transitory computer-readable medium of claim 15, wherein themachine-executable instructions, when executed by the processor, causethe computing device to perform at least the operations of: identifyinga selection of a payment instrument from a digital wallet; andtransmitting the selection of the payment instrument to a wallet serviceprovider for the purchase transaction request.
 17. The non-transitorycomputer-readable medium of claim 16, wherein the machine-executableinstructions, when executed by the processor, cause the computing deviceto perform at least the operations of: transmitting to the walletservice provider a user credential for authentication of the paymentinstrument; and receiving transaction security data from the walletservice provider in response to authentication of the paymentinstrument.
 18. The non-transitory computer-readable medium of claim 17,wherein the transaction security data comprises an unpredictable numbergenerated by the wallet service provider, wherein the LUPC is generatedbased at least in part on the unpredictable number.
 19. Thenon-transitory computer-readable medium of claim 16, wherein themachine-executable instructions, when executed by the processor, causethe computing device to perform the providing of the in-app paymentcryptogram to the merchant application which further cause the computingdevice to perform at least the operation of providing a token associatedwith the payment instrument to the merchant application.
 20. Thenon-transitory computer-readable medium of claim 15, wherein the LUPC isa session key configured to authorize a purchase using a digital walleton the computing device.